Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement backward case in haskell-forward-sexp #1158

Merged
merged 1 commit into from
Feb 16, 2016
Merged

Implement backward case in haskell-forward-sexp #1158

merged 1 commit into from
Feb 16, 2016

Conversation

cruegge
Copy link
Contributor

@cruegge cruegge commented Feb 15, 2016

I implemented the backward case, basically according to your hints in #759. The main difference is that I do not skip back to whitespace, but use plain backward-sexp, which also properly skips over parens.

@cruegge
Copy link
Contributor Author

cruegge commented Feb 15, 2016

Regarding the coverage error: shoud I add some tests?

@gracjan
Copy link
Contributor

gracjan commented Feb 15, 2016

Yes, tests for negative argument are needed. We need both passing and failing tests.

@cruegge
Copy link
Contributor Author

cruegge commented Feb 15, 2016

I'm sorry, I don't fully understand the concept of failing tests. Are those test that fail prior to the commit and should be non-failing afterwards? So the test basically describes desirable behaviour, and it is "expected to fail" for stuff that's not implement properly yet?

@gracjan
Copy link
Contributor

gracjan commented Feb 15, 2016

In this case I mean a case that goes backward-sexp but hits an opening parenthesis. Sorry about confusion.

gracjan added a commit that referenced this pull request Feb 16, 2016
Implement backward case in haskell-forward-sexp
@gracjan gracjan merged commit 7fbd4ee into haskell:master Feb 16, 2016
@gracjan
Copy link
Contributor

gracjan commented Feb 16, 2016

Nice! Thanks!

@gracjan gracjan mentioned this pull request Feb 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants